SGTP Schema Statistics


SGTP Schema Statistics
 
The SGTP schema provides operational statistics that can be used for monitoring and troubleshooting the following products: SGSN
This schema provides the following types of statistics:
Counter: A counter records incremental data cumulatively and rolls over when the counter limit is reached.
Gauge: A gauge statistic indicates a single value; a snapshot representation of a single point in time within a defined time frame. The gauge changes to a new value with each snapshot though a value may repeat from one period to the next. The limit depends upon the data type.
Information: This type of statistic provides information, often intended to differentiate sets of statistics; for example, a VPN name or IP address. The type of information provided depends upon the data type.
The data type defines the format of the data for the value provided by the statistic. The following data types are used in statistics for this schema:
Int32/Int64: An integer, either 32-bit or 64-bit:
Float: A numeric value that can be represented fractionally; for example, 1.345.
String: A series of ASCII alphanumeric characters in a single grouping, usually pre-configured.
note_smallImportant: Unless otherwise indicated, all statistics are counters and all statistics are standards-based.
Key Variables: Every schema has some variables which are typically referred to as 'key variables'. These key variables provide index markers to identify which object the statistics apply to. For example, in the card schema, the card number (variable %card%) uniquely identifies a card. For an HA service, the keys would be "%vpnname%" plus "%servname%", as the combination uniquely identifies an HA service. So, in a given measurement interval, one row of statistics will be generated per unique key. The schema keys are identified in the Description section of the table.
Bulk Statistic Variables in the SGTP Schema
Description: Total number of GTP-U messages bytes sent to GGSN at a given instance of time.
Triggers: Changes every time an uplink packet is sent to the GGSN.
Availability: Across all SGTP services, per SGTP service, per GGSN
Description: Total number of bytes for GTP-U messages sent to the RNC at a given instance in time.
Triggers: Changes every time a downlink packet is sent to the RNC.
Availability: Across all SGTP services, per SGTP service, per RNC
Type: Counter
Description: Total number of GTP-U message bytes sent to the peer SGSN at a given instance of time.
Triggers: Changes every time a packet is sent to a “new” SGSN during an Inter SGSN handoff.
Availability: Across all SGTP services, per SGTP service
Type: Counter
Description: Total number of GTP-U message bytes received from the GGSN at a given instance of time.
Triggers: Changes every time a downlink packet is received from the GGSN.
Availability: Across all SGTP services, per SGTP service, per GGSN
Type: Counter
Description: This proprietary counter indicates the total number of packets that are forwarded from the GGSN queue.
Triggers: Increments when a packet is forwarded from the GGSN queue.
Availability: Per SGTP service
Type: Counter
Description: This proprietary counter indicates the total number of bytes that are forwarded from the GGSN queue.
Triggers: Increments when a byte is forwarded from the GGSN queue.
Availability: Per SGTP service
Type: Counter
Description: Total number of downlink packets that were queued but dropped due to IU/RAB release.
Triggers: Counter at the new SGSN increments when Iu/RAB gets released while inter-SGSN-RAU is in progress and downlink data is queued during RAU.
Availability: Per SGTP service
Type: Counter
Description: Total number of downlink bytes that were queued but dropped due to IU/RAB release.
Triggers: Counter at the new SGSN increments when Iu/RAB gets released while inter-SGSN-RAU is in progress and downlink data is queued during RAU.
Availability: per SGTP service
Type: Counter
Description: Total number of downlink packets that were queued but dropped due to T3-tunnel timer expiry during inter-SGSN RAU procedure.
Triggers: During inter-SGSN RAU at the old SGSN, neither Cancel Location or SGSN Context Ack are received when t3-tunnel timer is fired causing the RAU procedure to abort. If old RABs are not available, the data queued during the RAU will be dropped.
Availability: per SGTP service
Type: Counter
Description: Total number of downlink bytes that were queued but dropped due to T3-tunnel timer expiry during inter-SGSN RAU procedure.
Triggers: During inter-SGSN RAU at the old SGSN, neither Cancel Location or SGSN Context Ack are received when t3-tunnel timer is fired causing the RAU procedure to abort. If old RABs are not available, the data queued during the RAU will be dropped.
Availability: per SGTP service
Type: Counter
Description: This proprietary counter indicates the total number of packets that are dropped from the GGSN queue, because of BVC Block or BVC Reset messages received for the MM context.
Triggers: Increments when a packet is dropped from the GGSN queue because of BVC Reset/BVC Block received for the MM context.
Availability: per SGTP service
Type: Counter
Description: This proprietary counter indicates the total number of bytes that are dropped from the GGSN queue, because of BVC Block or BVC Reset messages received for the MM context.
Triggers: Increments when a byte is dropped from the GGSN queue because of BVC Reset/BVC Block received for the MM context.
Availability: per SGTP service
Type: Counter
Description: Total number of GTP-U messages bytes received from the RNC at a given instance of time.
Triggers: Increments when SGSN receives an uplink packet from an RNC.
Availability: Across all SGTP services, per SGTP service, per RNC
Type: Counter
Description: Total number of “invalid” packets received from GGSN or RNC with errors due to mismatch in payload length.
Triggers: Increments when received GTP-U (v1 and v0) header does not match with the actual payload length field.
Availability: Across all SGTP services, per SGTP service
Type: Counter
note_smallImportant: See Bulk Statistics Overview for statistics that are common to all schema.
 
 

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883